TR
11111

COURSE INTRODUCTION AND APPLICATION INFORMATION

se.cs.ieu.edu.tr

Course Name
Code
Semester
Theory
(hour/week)
Application/Lab
(hour/week)
Local Credits
ECTS
Fall/Spring
Prerequisites
None
Course Language
Course Type
Elective
Course Level
-
Mode of Delivery -
Teaching Methods and Techniques of the Course Group Work
Problem Solving
Course Coordinator
Course Lecturer(s)
Assistant(s) -
Course Objectives
Learning Outcomes The students who succeeded in this course;
  • Students will have knowledge of basic concepts of professional software development and ethics
  • Students will have knowledge of stages of software development
  • Students will have knowledge of interviewing and negotiation with clients for requirement gathering
  • Students will have knowledge of software process models
  • Students will be able to classify functional and non-functional requirements
  • Students will be able to draw UML diagrams such as Use-Case, Sequence, Activity, Class diagrams and State charts appropriate to requirements
  • Students will have knowledge of concepts and types of systems architecture
  • Students will be able to use Object Oriented architecture components
  • Students will be able to design system architecture using specification documents
  • Students will have knowledge of Black and White box tests
  • Students will have knowledge of software maintenance tasks
Course Description

 



Course Category

 Core Courses
X
Major Area Courses
Supportive Courses
Media and Managment Skills Courses
Transferable Skill Courses

 

WEEKLY SUBJECTS AND RELATED PREPARATION STUDIES

Week Subjects Required Materials
1 Introduction Software Engineering Sommerville – Ch1
2 Software processes Software Engineering Sommerville – Ch2
3 Software processes Software Engineering Sommerville – Ch2
4 Agile software development Software Engineering Sommerville – Ch3
5 Requirements engineering Software Engineering Sommerville – Ch4
6 Requirements engineering Software Engineering Sommerville – Ch4
7 System modeling Software Engineering Sommerville – Ch5
8 Midterm Exam
9 Architectural design Software Engineering Sommerville – Ch6
10 Architectural design Software Engineering Sommerville – Ch6
11 Design and Implementation Software Engineering Sommerville – Ch7
12 Software Testing Software Engineering Sommerville – Ch8
13 Software Evolution Software Engineering Sommerville – Ch9
14 Overivew Software Engineering Sommerville – Ch1..Ch9
15 Overivew Software Engineering Sommerville – Ch1..Ch9
16 Review of the Semester  
Course Notes/Textbooks Software Engineering 9, Ian Sommerville, 9th Ed. Addison Wesley, 2010, ISBN 0137053460
Suggested Readings/Materials Software Engineering APractitioners’s Approach, Roger S. Pressman, McGrawHillPublishing Co.; 7th Ed edition (2009), ISBN: 9780071267823

 

EVALUATION SYSTEM

Semester Activities Number Weigthing
Participation
Laboratory / Application
1
10
Field Work
Quizzes / Studio Critiques
Portfolio
Homework / Assignments
Presentation / Jury
Project
1
30
Seminar / Workshop
Oral Exam
Midterm
1
25
Final Exam
1
35
Total

Weighting of Semester Activities on the Final Grade
65
Weighting of End-of-Semester Activities on the Final Grade
35
Total

ECTS / WORKLOAD TABLE

Semester Activities Number Duration (Hours) Workload
Course Hours
(Including exam week: 16 x total hours)
16
2
32
Laboratory / Application Hours
(Including exam week: 16 x total hours)
16
Study Hours Out of Class
15
1
Field Work
Quizzes / Studio Critiques
Portfolio
Homework / Assignments
1
Presentation / Jury
Project
1
Seminar / Workshop
Oral Exam
Midterms
Final Exams
1
13
    Total
60

 

COURSE LEARNING OUTCOMES AND PROGRAM QUALIFICATIONS RELATIONSHIP

#
 Program Competencies/Outcomes
* Contribution Level
1
2
3
4
5
1 Be able to define problems in real life by identifying functional and nonfunctional requirements that the software is to execute X
2 Be able to design and analyze software at component, subsystem, and software architecture level X
3 Be able to develop software by coding, verifying, doing unit testing and debugging X
4 Be able to verify software by testing its behaviour, execution conditions, and expected results X
5 Be able to maintain software due to working environment changes, new user demands and the emergence of software errors that occur during operation X
6 Be able to monitor and control changes in the software, the integration of software with other software systems, and plan to release software versions systematically X
7 To have knowledge in the area of software requirements understanding, process planning, output specification, resource planning, risk management and quality planning
 X
8 Be able to identify, evaluate, measure and manage changes in software development by applying software engineering processes X
9 Be able to use various tools and methods to do the software requirements, design, development, testing and maintenance X
10 To have knowledge of basic quality metrics, software life cycle processes, software quality, quality model characteristics, and be able to use them to develop, verify and test software X
11 To have knowledge in other disciplines that have common boundaries with software engineering such as computer engineering, management, mathematics, project management, quality management, software ergonomics and systems engineering X
12 Be able to grasp software engineering culture and concept of ethics, and have the basic information of applying them in the software engineering X
13

Be able to use a foreign language to follow related field publications and communicate with colleagues

 X

*1 Lowest, 2 Low, 3 Average, 4 High, 5 Highest

 

İzmir Ekonomi Üniversitesi | Sakarya Caddesi No:156, 35330 Balçova - İZMİR Tel: +90 232 279 25 25 | webmaster@ieu.edu.tr | YBS 2010